-
Notifications
You must be signed in to change notification settings - Fork 1k
[docs] Automatically generate documentation from JSDoc #76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Fixes a few issues in their parser Fork: https://github.com/xenova/catharsis Original: https://github.com/hegemonic/catharsis
|
Currently the output looks like: I dislike the dot syntax in the so called "type application": Should we just remove the dots (they are applied in both And then about the output... right now it's just one big file, does it need to be many smaller files? I couldn't find an option for that, probably that would require some API scripting. |
Agreed. Not too sure why they do that. Apparently it's an older syntax. That sounds like the easiest solution, yeah.
I was looking at this yesterday, and I also couldn't find a way to do it from the CLI. Do you think we should do it on a file basis or a class basis? I'm trying to make it similar to huggingface.js' docs, which splits each class into a separate file. This looks like it could work: https://github.com/jsdoc2md/jsdoc-to-markdown/wiki/How-to-create-one-output-file-per-class ? |
Hm, many projects already assume that one file = one class, but I guess you want to keep them all in one huge file? Per-class-separation sounds better to me too. Also worked out the PR that at least |
For the most part, I'd actually prefer it to be separated... especially for the really large files. What about something like this: docs/
Not too sure if "functions"/"classes" are the way to break it up more though. |
I personally prefer that approach as well. Keeping this library's docs consistent with the HF docs will be better for the Dev experience overall. |
Determine method to quantize based on supported operations
Will switch back to main doc-builder after some issues are resolved
Will remove after merged
This means the script must be run from the project's root folder
GitHub actions places files in a folder called `__w`, which causes JSDoc to ignore all source files. See jsdoc2md/jsdoc-to-markdown#137
Also adds support for: 1. `Prepend` normalizer 2. Chained decoding 3. Byte fallback
Also add unit test for decoding with and without special tokens
|
The documentation is not available anymore as the PR was closed or merged. |

Making a draft PR for comments and suggestions!